Systems and methods for distributing content using attributes

ABSTRACT

Methods and apparatus for distributing content between fixed and nomadic servers using attributes. Attributes may relate to, inter alia, the type of content, location of a fixed and/or nomadic content server, a vehicle that includes a nomadic server, an ability to use content, a need for content, vehicle owner information, and/or time.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 61/354,777 filed Jun. 15, 2010 herein incorporated byreference.

FIELD OF THE INVENTION

Embodiments of the present invention relate to computers, communicationequipment, networks, and distributing content (e.g., data, information,electronic files) to content servers (e.g., stationary, mobile,roaming).

BACKGROUND OF THE INVENTION

Many types of vehicles (e.g., plane, car, truck) carry some type of acomputer (e.g., processing circuit, server, workstation) that providescontent to the occupants of the vehicle. In some cases (e.g., aircraft,trail, bus, maintenance vehicles), continuous communication to providecontent to or receive content from the vehicle is not possible; however,content may be provided to the vehicle or received from the vehicle atcertain fixed physical locations (e.g., airports, maintenance yards,fueling stations, bus terminals, train stations). Because the physicallocations may vary (e.g., different airports, different yards, differentfueling stations, different terminals, different stations), content fordelivery to the vehicle may need to be distributed to differentlocations depending on the route or schedule of the vehicle. Further,content may need to be delivered to a location prior to arrival of thevehicle, so that the content may be delivered to the vehicle during thelimited time that the vehicle will be at the physical location.

BRIEF DESCRIPTION OF THE DRAWING

Embodiments of the present invention will now be further described withreference to the drawing, wherein like designations denote likeelements, and:

FIG. 1 is a function block diagram of a system for distributing contentaccording to various aspects of the present invention;

FIG. 2 is a functional block diagram of a hierarchy of servers fordistributing content according to various aspects of the presentinvention;

FIG. 3 is another functional block diagram of a hierarchy of servers fordistributing content according to various aspects of the presentinvention;

FIG. 4 is a method for distributing content in accordance with a set ofattributes according to various aspects of the present invention;

FIG. 5 is another method for distributing content in accordance with aset of attributes according to various aspects of the present invention;

FIG. 6 is a function block diagram of a system for inserting content andan associated set of attributes according to various aspects of thepresent invention into a network for distribution;

FIG. 7 is another function block diagram of a system for insertingcontent and an associated set of attributes according to various aspectsof the present invention into a network for distribution;

FIG. 8 is another function block diagram of a system for insertingcontent and an associated set of attributes according to various aspectsof the present invention into a network for distribution; and

FIG. 9 is a function block diagram of a system for extracting contentfrom a network in accordance with a set of attributes according tovarious aspects of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A computer (e.g., processing circuit, server, workstation) may store,provide (e.g., transmit, transfer), and/or receive content. A computerthat stores, provides, and/or receives content is herein referred to asa content server. A content server may communicate (e.g., provide,transmit, receive) content via a conventional network (e.g., IEEE 802.3Ethernet, IEEE 802.11 wireless LAN, IEEE 802.13 100Baxe-X, IEEE 802.16WiMax, Bluetooth, optical). A computer may include any conventionaldevice (e.g., base station, access point, router, hub, switch,application software) for communicating content. A communicating devicemay include any conventional transducer (e.g., pressure, altitude, fuelgauge, temperature, stress, strain gauge, rpm). A content server mayreceive content from storage media (e.g., disk drive, USB drive, CDROM).

A vehicle may include a content server. A content server on (e.g., in, apart of, contained within, position on, located in) a vehicle is hereinreferred to as a nomadic content server or a nomadic server. A contentserver that does not move or moves infrequently is referred to herein asa fixed content server, fixed server, stationary content server,stationary server, infrastructure content server, and/or infrastructureserver. The phrase content server without the modifiers fixed,stationary, infrastructure, and/or nomadic refer to both fixed andnomadic content servers.

A nomadic content server may provide content to occupants of thevehicle. A nomadic content server may receive content from occupants ofthe vehicle, people who provide services to a vehicle (e.g.,maintenance, loading, crew, owner, operator), and/or the vehicle itself(e.g., operating information, vehicle performance, vehicle systemoperation). A vehicle may provide content to a nomadic content servervia transducers.

Content may include binary data, analog data, numbers, signals,characters, or any convention data and/or information. Content may bestored, subdivided, and/or organized in any conventional mannerincluding as raw data (e.g., as received without being processed ororganized), media (e.g., JPG, MPEG), documents, files, filing systems(e.g., hierarchical, flat), packets, and/or databases. Content may beused for any purpose including to entertain ((e.g., movies, news,sports, documentaries, advertising, music), create a vehicle maintenancerecord, provide a record of vehicle operation, provide instructions tooperators of the vehicle, and provide information about a destination ofthe vehicle.

In an implementation, content is organized as packages. A packagecontains a unit of content. A unit of content may include data for amovie, a musical number, a maintenance record, an equipment log, a crewtraining segment, a passenger manifest, and a baggage inventory. Apackage may be subdivided into one or more package items. A package itemmay include a document, a file, a packet, data, and/or content plusassociated metadata organized in any conventional manner. A package itemmay include a file that contains all or a portion of the data for theunit of content. A package may include one or more package items. Apackage may further include metadata that describes the package. Packageitems of a package may be individually distributed through a network andreassembled at a content server to form the package. Package items maybe numbered to show a sequence of a package item with respect to otherpackage items. A package may include indicia of the total number ofpackage items of the package. A content server may detect the arrival ofeach package item. A content server may detect the arrival of allpackage items.

Content may be distributed (e.g., sent, transmitted, provided, received,accepted transferred) via a network. Content may be distributed betweencontent servers. For example, a content server may receive content froma content provider (e.g., movie studios, radio stations, contentaggregators, vehicle owners, vehicle operators, destination operators,vehicle). One content server may provide content to another contentserver. One content server may provide content to multiple other contentservers. A content server may provide content to a content consumer(e.g., vehicle occupant, vehicle owners, vehicle operators, destinationoperators, vehicle).

Content may be provided to a content server via a wired connection. Acontent server may receive content from storage media via a wiredconnection. A nomadic content server may receive content prior toinstallation in a vehicle. For example, a conventional personal computer(e.g., desk top, mobile) may function as a nomadic content server thatreceives content in one location, is transported to a vehicle, andoperates as a nomadic content server once positioned in the vehicle.Prior to positioning the computer in a vehicle, the computer may receivecontent and attributes via a wired network, a wireless network, or aconventional bus (e.g., USB, 1394). Content and attributes may be storedon the computer hard disk drive. The computer may be physicallytransported to the vehicle thereby transporting the content stored onthe computer hard drive. Such a nomadic content server is referred to asa “content mule.” A content mule may be used in areas where using anetwork connection (e.g., wired, wireless) between a fixed contentserver and a nomadic content server positioned in a vehicle isexpensive. The mule may receive content in an environment where transferis inexpensive, then physically transported to the vehicle where themule performs the functions of a nomadic content server.

While in route, a nomadic server may be limited (e.g., physicallocation, duration) in the manner in which the nomadic server maydistribute content. For example, while in route, a nomadic contentserver may be disconnected from the network of fixed content servers andmay not send content to or receive content from fixed content servers.While in route, a nomadic content server may be distant from othernomadic content servers thereby precluding establishing communicationwith other nomadic servers to distribute content. While in route, anomadic content server may provide information to content consumers(e.g., extraction) and receive content from content providers (e.g.,insertion) that are in the vehicle that carries the nomadic server. Anomadic server may establish communication with a network of fixedcontent servers or other nomadic servers at locations (e.g., airports,maintenance yards, stations, rest stops, fueling stations, busterminals, train stations) along a route. The time that a nomadic serverstops at a location where it may communicate with other content serversmay be brief, so even when a nomadic server can establish a connectionwith other content servers, the duration of the communication may belimited.

Other factors may limit distribution of content to and from a nomadicserver. The length of a route traveled by a nomadic server may be long(e.g., worldwide) and the locations where a nomadic server may stop enroute to establish communication with other content servers may beseparated by large distances. The network between fixed servers at thevarious locations where the nomadic server may stop may be slow (e.g.,low data transfer rate), intermittent (e.g., unreliable), and/or costlyto use. Furthermore, the amount (e.g., bytes) of content for transfer toand/or from a nomadic content server may be large (e.g., gigabytes,megabytes) such that content may not transit the network to a contentserver at a location if sent just prior to the arrival of the nomadiccontent server at the location.

Considering the limitations of providing content to and receivingcontent from a nomadic server, content may need to propagate through anetwork of content servers so that content intended for a specificnomadic server arrives at a location where the nomadic server will stopbefore the arrival time of the nomadic server at the location.Distribution of content through a network and between content serversmay be accomplished in accordance with a schedule of the movements ofnomadic servers. Distribution of content to a location where a nomadicserver may stop and may establish communication with other contentserver may be accomplished by distributing content in accordance withone or more attributes. An attribute may incorporate the schedule and/orlocations of movement of a nomadic server. An attribute may include acharacteristic (e.g., quality, description) of a vehicle that carries anomadic server.

For example referring to FIG. 1, system 100 for distributing contentbetween content servers may include AirSync Server 110; fixed contentservers 140, 142, 144, 146, and 148; one or more content provider 130;and one or more schedule provider 120; network 170; and nomadic server150.

An AirSync Server includes one or more servers and software applicationsdeployed on content servers and communication equipment for provisioningthe network, provisioning users, monitoring network performance,providing quality of service in accordance with provisioning, managingthroughput, and measuring performance of system 100 and components ofsystem 100. An AirSync Server may detect whether a server is connectedto the network. An AirSync Server may detect whether a content server isconnected to the network.

Content servers 140, 142, 144, 146, 148, and 150 may perform thefunctions of a content server as discussed above. Content server 142,144, and 146 are positioned at distinct physical location nos. 1, 2, andN respectively. One or more contents servers may be positioned at eachphysical location.

Nomadic server 150 may travel a route that includes stops at locations1, 2 and N. A nomadic server need not stop at each location where afixed server of a network of servers is located. The locations where anomadic server stops may correspond to a schedule of transit such as anairline, train, or bus schedule. Nomadic server 150 may establishcommunication with content servers 142, 144, and 146 via communicationlink 160, 162, and 164 respectively at locations 1, 2 and Nrespectively. A nomadic server may establish communication with acontent server while the nomadic server is positioned at the physicallocation of the content server.

A medium of communication may determine the distance between a nomadicserver and a fixed server for establishing communication. Communicationover wired connection may require a wire to extend directly from thephysical location to the nomadic server. A wireless connection maypermit communication at a greater distance. For example, a wiredconnection may require an airplane to be positioned at a gate of anairport to establish the connection. A wireless connection may permitcommunication with the airplane after landing, but prior to arriving ata gate. While a nomadic server is in transit between physical locations,the nomadic server may be out of range of all fixed server such that thenomadic server cannot communicate with any fixed server.

A schedule provider provides a schedule. A schedule may includetimetable of the movements of one or more vehicles with their nomadiccontent servers. A schedule may include a time, a date, and acorresponding predicted location of a nomadic server. A time and datemay indicate a time and date of arrival and/or departure of a nomadicserver to and/or from a location. A schedule may provide an estimatedduration that a nomadic server may stop at a location. A duration of astop of a nomadic server at a location may be an indication of aduration of communication between a nomadic server and a fixed server atthe location. A schedule provider may provide a schedule to contentserver.

Attributes associated with a content server and/or content may beselected in accordance with a schedule (e.g., itinerary). A value of anattribute may be set in accordance with a schedule. Content may bedistributed to a fixed content server at a location in advance of thearrive of a nomadic content server by using attributes and attributevalues set in accordance with a schedule. Attributes and attributevalues may be set so that content is distributed to a content server ata physical location in advance of the arrival of a nomadic server.

A content provider provides content for distribution between and/or tocontent servers. Content provided by a content provider may bedistributed in accordance with one or more attributes as discussedherein. A content provider may develop content using a system that isexternal to the network. A content provider may provide content to thenetwork and content servers of the network via a process referred tobelow as insertion. A content provider may insert content and/orattributes for content into a network for distribution. A contentprovider may cooperate with a manager of a network to configureattributes for routing content.

In an implementation, schedule provider 120 provides a schedule tocontent server 148. The schedule provided by schedule provider 120indicates date 1 and time 1 for arrival of nomadic server 150 atlocation no. 1, date 2 and time 2 for arrival of nomadic server 150 atlocation no. 2, and date N and time N for arrival of nomadic server 150at location no. N. Duration 1, 2, and N, whether provided in theschedule or calculated from an arrival and departure time, provides apredicted duration of the stop of nomadic server at locations nos. 1, 2,and N respectively. A schedule may further provide information as to apredicted position (e.g., gate, bay) of nomadic server 150 at alocation. Attributes associated with content may be configured inaccordance with the schedule, predicted duration of a stop, and anamount (e.g., bytes) of content for delivery to progressively delivercontent to nomadic server 150 as it arrives at location nos. 1, 2, andN. Attribute values of content may be configured to deliver an amount ofdata at each stop along the route of nomadic server 150.

In this example, nomadic server 150 may arrives at location no. 1 atdate 1 and time 1. Nomadic server 150 remains at location no. 1 forduration 1. During duration 1, nomadic server establishes communicationusing link 160 with content server 142 and sends and/or receivescontent. After leaving location no. 1 and while en route to location no.2, nomadic server is disconnected from content servers 140, 142, 144,146, and 148. Nomadic server 150 arrives at location no. 2 on date 2 attime 2 and establishes communication with content server 144 via link162 during duration 2 to send and receive content. Nomadic servercontinues along its route, stopping at various locations to send andreceive content, until it arrives at location no. N. At location no. N,nomadic server 150 communicates with content server 146 to send andreceive content via link 164 for duration N.

Content may be distributed to content servers 142, 144, and 146 fordelivery to nomadic server 150 prior to the arrival of nomadic server150 at a location. Because the amount of content for delivery to nomadicserver 150 may be too much for transfer at a single location, contentmay be delivered to content servers along the route of nomadic contentserver 150 for incremental delivery to nomadic server 150 at eachlocation. Content may further be distributed for timely delivery to anomadic server. For example, while nomadic server 150 is in transit fromlocation no. 1 to location no. 2, it does not receive content. A contentprovider may provide content (e.g., news) that occurred while nomadiccontent server 150 was travelling from location no. 1 to location no. 2.The timely content may be provided to content server 144 prior toarrival of nomadic server 150 at location no. 2. Upon arrival atlocation no. 2, nomadic server 150 receives the timely content for usein the vehicle that transports nomadic server 150. In such a situation,a content provider and/or a manager of the network may set theattributes of content for delivery to a specific fixed content server(e.g., 144) prior to the predicted arrival time of nomadic server 150.

In another example, all content that may need to be delivered to nomadiccontent server 150 is routed to content servers 142, 144, and 146.Because content servers 142, 144, and 146 store all data for delivery tonomadic server 150, a change in the duration that nomadic server 150 isat a physical location may be compensated for by the other fixedservers. For example, if duration 1 is larger than expected due to adelay, the content servers 144 or 146 do not need to deliver as muchcontent. In another example, if duration 2 is short or zero due to aninfrastructure issue such as equipment failure or excessive cost toestablish link 162, content servers 142 and 146 may make up forproviding little or no content at location no. 2. Nomadic content server150 may track the amount of content received and report to a fixedserver the remaining package items that should be delivered.

As discussed above, distribution of content between content servers maybe accomplished using one or more attributes. A fixed content server mayinclude a set of attributes. A set of attributes may include one or moreattributes. Each attribute may have one or more values. A nomadic servermay include a set of attributes. Content, in particular a package item,may include a set of attributes. A vehicle may include a set ofattributes. An attribute of a vehicle may include a characteristic ofthe vehicle and/or a descriptor associated with a use of the vehicle.

The attributes of a nomadic server may include one or more of theattributes of the vehicle that carries the nomadic server. Theattributes of a fixed server may include one or more attributes of thevehicles that carry nomadic content servers that may communicate at sometime with the fixed content server. The attributes of a package item mayinclude one or more attributes of the vehicle that may consume thecontent of the package item. In one implementation, a package item thatincludes an attribute related to a vehicle may be routed through anetwork of fixed servers for delivery to a nomadic server that on avehicle.

As discussed above, a nomadic content server may be positioned on avehicle. A vehicle may include one or more attributes. An attribute fora vehicle may include a vehicle identification number, an operatoridentifier, a vehicle owner identifier, and/or a function of a vehicle.

For example, in the case of an airplane, a vehicle attribute may includea tail number, a type, a model, a vendor, an airline that operates theairplane, a flight number, a home airport, a present airport, and a gatenumber. In the case of a maintenance vehicle, a vehicle attribute mayinclude maintenance specialty (e.g., electrical, plumbing, roofing), avehicle number, a job number, a job description, job type, and adestination. In the case of a train, a vehicle attribute may include atrain number, a track, a direction of travel, a destination, a haulidentifier (e.g., local, long distance), and a station identifier.

A value for an attribute may be provided by network server (e.g.,AirSync), a vendor of equipment (e.g., content server, vehicle), acontent provider, a content server that receives content from a contentprovider (e.g., insertion server), a vehicle operator, a vehicle owner,a system user.

Attributes for a fixed server, a nomadic server, and content (e.g.,package, package item) may include the same and/or different attributes.An attribute may provide information about a content server,communication equipment, a system external to the content servernetwork, a location, a position at a location, a geographic coordinate,a vehicle, a vehicle owner, a vehicle operator, a purpose of a vehicle,an assignment of a vehicle, and a route.

An attribute of a package item may be related to the content of thepackage item. For example, an attribute of a package item may include adescription of the content (e.g., video, music, data). An attribute of apackage item may be unrelated to the content of the package item. Forexample, an attribute of a package item may be a vehicle attribute.

Attributes and/or values of attributes for content servers may be fixed,static, or dynamic. A fixed attribute is an attribute whose value doesnot change over the life of the equipment (e.g., content server,vehicle). A fixed attribute value may be set by an equipmentmanufacturer, a person who configures a system (e.g., network, contentserver), and/or a manager of the network.

A static attribute may include attributes whose values are set uponinitialization of a content server. Static attributes include attributesvalues that are configured by a user and/or network manager whileinitializing a device.

Dynamic attributes may include attributes whose values change over time.The value of a dynamic attribute may change responsive to the operation(e.g., use) of a vehicle, a change in schedule, and/or a change in thenetwork. Values for dynamic attributes may be provided by systems of thevehicle, the vehicle operator, and/or the system operator (e.g.,manager). The value of dynamic attributes may be reported to the server(e.g., server 110, 210). Some attributes are required in a set ofattributes while others are not.

The value of an attribute may be referred to as an attribute as opposedto an attribute name and a value for the attribute name.

In an implementation that distributes content to aircraft, a set ofattributes for a fixed content server may include the attributesprovided in Table 1. A fixed content server may include some or all ofthe attributes of Table 1 through Table 4.

TABLE 1 Attributes for a Fixed Content Server Attribute Name TypeDescription Universal Unique Fixed A unique identifier of the contentserver. Identifier (UUID) or May be provided by an equipment contentserver manufacturer or a user who configures a identifier system. Devicetype Fixed Content server type. Device model Fixed Content server model.Device vendor Fixed Content server vendor. External system ID StaticUnique identifier of an external system (e.g., TopEffects!) served bythe content server. Not required of the content server does not servicean external system. External system Static Software revision of externalsystem. software revision Not required of the content server does notservice an external system. Content server area Static An area code fornetwork partitioning. The value and range of the code depends on thesubdivisions of a geographic area (e.g., entire planet, a continent, acountry, a region). Gate number Static The gate number (e.g., gate at anairport) at which the content server is located (e.g., deployed,positioned). This value may not be applicable to content servers notlocated proximate to a gate. Airport Static Airport at which the contentserver is located. This value may not be applicable to content serversnot located proximate to an airport or that distributes content to morethan one airport. Geographic Static A coordinate (e.g., lat/long, UTM)that coordinate describes the geographic location of the content server.Industry alliance Static Name of industry alliance associated with theaircraft. Airline Static Name of airline that operates the aircraft.

In an implementation that distributes content to aircraft, a set ofattribute for a nomadic content server may include some or all of theattributes of Table 2. A set of attributes for a fixed content servermay further include any or all of the attributes of Table 2. A set ofattributes for a nomadic content server may further include some or allof the attributes provided in Tables 3 and 4.

Attributes for a vehicle that carries (e.g., transports, moves) anomadic content server may include some or all of the attributesprovided in Table 2. For example, an aircraft may include attributes andthe associated values for aircraft tail number, aircraft type, aircraftmodel, aircraft vendor, aircraft configuration, on-board systemidentifier, and on-board system software revision. A value of anattribute for a nomadic contents server may be the same as the value ofthe attribute for the vehicle that carries the content server.

TABLE 2 Attributes for a Nomadic Content Server Attribute Name TypeDescription Aircraft tail Fixed A unique identifier used to identify thenumber content server located on the aircraft. Aircraft type Fixed Typeof aircraft. Aircraft model Fixed Model of aircraft. Aircraft vendorFixed Vendor of aircraft Industry alliance Static Name of industryalliance associated with the aircraft. Airline Static Name of airlinethat operates the aircraft. Aircraft Static Indicates the type offlights provided by configuration the aircraft (e.g., long-haul,regional, charter) On-board system Static A unique identifier of theon-board identifier system served by the nomadic content server.On-board systems may include in-flight entertainment systems thatreceive content from the nomadic server. On-board systems may furtherinclude crew and/or aircraft systems that provide content to the nomadiccontent server. On-board system Static Software revision of the on-boardsystem. software revision Content server Static An area code for networkpartitioning. area The value and range of the code depends on thesubdivisions of a geographic area (e.g., entire planet, a continent, acountry, a region). Home airport Static Name of airport at which theairplane is based. Flight number Dynamic The flight number presentlyassigned to the aircraft. The flight number is provided by the airline.Gate number Dynamic Gate number at which the aircraft is presentlypositioned. Present airport Dynamic Name of airport at which theaircraft is presently positioned. Flight segment/ Dynamic Flightconfiguration (e.g., city pair arrival/departure airport names) Onairport Dynamic The value of this attribute indicates whether theaircraft is positioned at the airport identified by the attribute“present airport.” The attribute may further indicate whether theaircraft is on the tarmac (e.g., wheels-on-ground); on the taxiway, onthe runway, or at the gate. Systems of the aircraft may provideinformation and/or signals to produce the values of this attribute.Unfinished Dynamic A package may include a number of package packageitems. Package items in a item identifier package may be identified bypackage item identifiers. A list of package item IDs may be provided toa nomadic content server, so the nomadic content server may verifyreceipt of each package item of the package even though delivery may beinterrupted or non-sequential. The unfinished package item identifier isone or more a packet item IDs of a package that a nomadic contentprovided has not received. Missing chunk Dynamic A package having morethan one package number item may be group the package items into chunks(e.g., groups) for delivery. A group may include one or more packageitems. A nomadic content receiver may receive some chunks at onegeographic location and other chunks at other geographic locations untilall the chunks have been received. Missing chunk number tracks theidentifiers (e.g., number) of the chunks of a package that have not beenyet received.

A set of attribute for a package item may include the attributesprovided in Table 3. Attributes for a package item may be mandatory(e.g., required) or not mandatory (e.g., not required). A set ofattributes for a package item may further include some or all of theattributes provided in Tables 1 and 2. A set of attributes for a packageitem may include attributes of a vehicle that carries a nomadic contentserver.

TABLE 3 Attributes for a Package Item Attribute Name MandatoryDescription Package identifier Yes Identifier for the package to whichthe package item belongs. A package identifier may be unique or may becombined with the package item identifier to form a unique identifier.Package item Yes Identifier for the package item. A identifier (e.g.,package item identifier may be unique packet item ID) or may be combinedwith the package identifier to form a unique identifier. Package itemYes The sequence number of the package sequence number item in thepackage. Last package item Yes Notification of the last package item ofa notification package. Size Yes Size in bytes of the package item datafile. Activation date Yes The date that the distribution of the packageitem to content servers should begin. The activation date may be definedas a duration (e.g., number of days) after the creation date. Deliverydate Yes The date by which delivery of the package item to all contentservers that should receive the package item should be complete. Thedelivery date may be defined as a duration (e.g., number of days) afterthe creation date. Expiration date Yes The date after which the packageitem will not longer be valid. The expiration date may be defined as aduration (e.g., number of days) after the creation date. Date last YesTimestamp of last modification made to modification the package itemdata and/or attribute. MD5 checksum Yes MD5 (e.g., cryptographic hash)checksum of the package item data file. Priority Yes Delivery priorityof the package. Each package item of a package has the same priority.Package item type Yes The type of content in the package item. Packagename No A name of the package. Source No The external system ID of theexternal system that originally provided the content. Creator No Theperson responsible for creating the package. Creation date No Date andtime of original creation. Package item name No Name of package item.Package item No An extended description of the package description item.Genre No Genre of content in the package (e.g., news, movie, music,firmware, maintenance data, flight information, crew information).Pre-distribution No List of actions for execution prior to scripttransmitting the package item. Post-distribution No List of actions forexecution after script transmitting the package item.

A set of attributes for a package item may further include attributesfor distributing the package item between content servers. Attributesused for distributing a package item may include any attribute assignedto a content server (e.g., fixed, nomadic). In an implementation thatdistributes content to aircraft, additional attributes for a packageitem may include some or all of the attributes provided in Tables 1, 2,and 4.

TABLE 4 Additional Attributes for a Package Item Attribute NameMandatory Description Airline No Name of airline or airlines that mayreceive the package item. Aircraft type No Type of aircraft that mayreceive the package item. Aircraft model No Model of aircraft that mayreceive the package item. Industry alliance No Name of industry alliancewhose aircraft may receive the package item. Airport No Name of airportwhere content servers are located or may be located in the future thatmay receive the package item. Gate number No Gate number at whichpackage item may be delivered. Used in conjunction with airport touniquely identify the gate location. Flight number No Flight number ofaircraft that may receive the package item.

Packages may be distributed throughout a network of content serversusing attributes. A content server may assess the attributes of apackage and/or package item to determine whether the content servershould take an action. An action may include storing the package item,forwarding the package item, providing a notice regarding the packageitem, and deleting the package item.

A content server may take an action in accordance with a result ofassessing an attribute. A content server may use a rule to assess theattributes of a package item. A rule may include any type of formula. Arule may include mathematical and/or Boolean formulas. A rule may beapplied to the attributes of a content server and/or the attributes of apackage item. A rule may provide a result in accordance with applyingthe rule. A rule may detect one or more attribute of a set ofattributes. A rule may detect one or more values of one or moreattributes. A rule may provide a result in accordance with detecting. Arule may compare all or a portion of the attributes and/or values ofattributes of a content server and a package item. A rule may provide aresult in accordance with comparing. A content server may take an actionbased on a match condition or a no match condition of applying a rule.

In an implementation referring to FIG. 2, network 200, according tovarious aspects of the present invention, includes server 210; fixedcontent servers 220, 222,224, 226, 228, 230, and 232; nomadic contentservers 250, 252, 254, 256, and 258; content insertion devices 270 and272; and content extraction device 278.

Fixed content servers 220, 222,224, 226, 228, 230, and 232 may performthe functions of a fixed content server described above. Fixed contentservers 220, 222,224, 226, 228, 230, and 232 include set of attributes234, 236, 238, 240, 242, 244, and 248 and rules 235, 237, 239, 241, 243,245, and 249 respectively. The acronym “FCS” may be used to indicate afixed content server.

Nomadic content servers 250, 252, 254, 256, and 258 may perform thefunctions of a nomadic content server described above. Nomadic contentservers 250, 252, 254, 256, and 258 include set of attributes 260, 262,264, 266, and 268 and rules 261, 263, 265, 267, and 269 respectively.The acronym “NCS” may be used to indicate a nomadic content server.

Content insertion device 270 and 272 perform the functions of aninsertion device discussed below. Content insertion device 270 and 272in cooperation with content server 232 and 230 respectively may performthe functions of an insertion system (e.g., 600, 700, 800) shown inFIGS. 6-8 and discussed below. Content extraction device 278 performsthe functions of an extraction device discussed below. Contentextraction device 278 in cooperation with content server 220 may performthe functions of an extraction system (e.g., 900) shown in FIG. 9 anddiscussed below.

A content insertion device (e.g., 270, 272) and a content extractiondevice (e.g., 278) may cooperate with any nomadic content server (e.g.,250, 252, 254, 256, 258) to insert content provided by a vehicle andextract content from a package item for use by the vehicle.

Server 210 may perform the functions of an AirSync Server discussedabove. A server may communicate with one or more contents servers ofnetwork 200. A server may communicate with a content server using anyconventional communications protocols, network and/or channels. In animplementation, server 210 communicates with network 214 over link 212.Content server 220 communicates with network 214 over link 216. A linkmay be wired or wireless. A network may include a private network and/orthe internet.

Each content server may communicate with one or more other contentservers, insertion devices, and/or extraction devices. A content servermay communicate using any conventional communications protocols,network, channels, and/or medium (e.g., wired, wireless). A contentserver may communicate using one or more channels to provide half-duplexor full-duplex communication. A content server may establish a dedicatedlink for communication or may share a link. A content server maycommunicate over a network. One or more content servers may communicateover the same network.

For example, communication connection 218 between content server 220 andcontent server 226 may be a direct wired and/or wireless connection ormay include a network and links to the network, of which network 214 andlinks 212 and 216 are an example. Communication connections betweenother content servers may be similar to communication connection 218.All links between contents servers may communicate through a networksuch as network 214. A link depicted as a “lightning bolt” represents awireless connection.

Content servers may be organized for distribution of content in anyconventional manner. In an implementation, the content servers ofnetwork 200 are organized in a parent-child relationship with respect toeach other. For example, content server 220 communicates with childrencontents servers 222, 224 and 226 and extraction point 278. Contentserver 224 communicates with children content servers 228 and 230.Content server 228 communicates with child content server 232. Contentserver 232 communicates with insertion device 270. Content server 230communicates with children content servers 256 and 258 and insertionpoint 272. Content server 222 communicates with children content servers250, 252, and 254.

An insertion device may provide content to a network of content servers.An insertion device may originate content. An insertion device mayprovide content originated from a source external to the network. Aninsertion device may provide a set of attributes associated withcontent. An insertion device may provide content as one or more packageitems. Each package item may include a set of attributes. An insertiondevice may provide content without a set of attributes and a receivingcontent server may provide a set of attributes for the content.

For example, insertion device 270 and 272 may include content 275 and277 respectively. Insertion device 270 and 272 assign set of attributes274 and 276 to content 275 and 277 respectively. Content 275 and 277 maychange. Attributes 274 and 276 may change in accordance with a change incontent 275 and 277. Insertion device 270 (272) provides content 275(277) and attribute 274 (276) to fixed content server 232 (230). Fixedcontent server 232 (230) distributes content 275 (277) throughoutnetwork 200 in accordance with attribute 274 (276). Additionalinformation regarding insertion devices and the insertion of content andattributes into a network is discussed below.

An extraction device may receive content from a network of contentservers. An extraction device may include a set of attributes toidentify content for receiving at the extraction device. An extractiondevice may include a rule for assessing the attributes of a package itemto determine whether to receive the package item. A rule may include thefunctions and characteristics of a rule as discussed above. Anextraction device may cooperate with a content server to extract contentfrom a network.

In an implementation, extraction device 278 includes set of attributes280 and rule 281. Extraction device applies rule 281 to attribute 280and to an attribute of a package item provided by fixed content server220 to determine whether to receive the package item. Upon receipt of apackage item, the content of the package item is transferred to content282. The content of 282 changes at each receipt of a package item.Attribute 280 and/or rule 281 may change to receive package items havingdifferent attributes. Another implementation of an extraction device andan extraction system is discussed below.

In a network in which contents servers and/or extraction devices areorganized in parent-child relationships, the set of attributes of aparent content server may include the set of attributes of all child(e.g., children, grandchildren, so forth) content servers and/orextraction devices beneath the parent content server. An attribute setof a parent server may include each attribute and/or attribute value foreach child content servers to enable the parent to detect and forwardcontent that should be received by the children of the parent. Anattribute set of a parent may include a subset of the child attributesthat in conjunction with a rule that permits the parent to accept forforwarding content that should be received by the children of theparent.

A network manager may initialize and maintain the attribute sets andvalues for the content servers in a network. Some values of an attributeset for a content server may be deduced by operation of the networkserver or updated automatically by server 210.

A parent content server may receive content in accordance with theattributes of the children content servers and/or extraction devicesbeneath the parent content server. A parent content server may forwardcontent to a child content server and/or extraction device in accordancewith the attributes of the child content server and/or extractiondevice. A parent content server may receive content in accordance withattributes of a child content server and/or extraction device andprovide content responsive to a request from a child content serverand/or extraction device.

For example, attribute 234 and rule 235 of content server 220 includesthe set of attributes and rule from fixed content servers 222, 224, 226,228, 230, 232, nomadic content servers 250, 252, 254, 256, and 258 andextraction device 278. Content server 220 may receive content inaccordance with attributes and rule of the children content servers andextraction devices. Content server 220 may provide content to childrenin accordance with the attribute and rule of each child because contentserver 220 receives content for the children. A content server need notreceive content that does not accord (e.g., match) with its set ofattributes and rule. Because a parent content server receives contentfor its children content servers, a parent content server may also notaccept content that the parent content server and the children contentserver do not wish to receive in accordance with their attributes.

A content server may receive and forward content that does not match theattributes of the content server to a parent content server for possibledistribution to a content server where a match may be found. Forexample, content server 232 receives all content provided by insertiondevice 270 regardless of attribute 274 of content 275. Content server232 applies rule 249 to attribute 248 and attribute 274. In the event ofa match, content server 232 retains (e.g., stores) a copy of content275. Content server 232 may further provide content 275 and attribute274 to parent content server 228 in the event that a match may occur foranother content server in the network. In the event that applying rule249 to attribute 248 and attribute 274 does not result in a match,content server 232 provides content 275 and attribute 274 to parentcontent server 228 in the event that a match occurs for another contentserver that is higher in the parent-child hierarchy in the network. In anetwork organized in parent-child relationships, each content serverthat receives content that does not match its attributes in accordancewith its rule, provides the content to its parent. Providing contentwith non-marching attributes to a parent may eventually distribute thecontent to a content server where a match does occur. Upon detecting amatch, the content server may retain a copy of the content anddistribute the content to the children of the content server where amatch occurs.

Examples of how distribution of content in a network organized withparent-child relationships help provide an understanding of contentdistribution in accordance with attributes. The examples provided belowdo not limit the scope of the claims to the specific examples, butprovide an example of one possible implementation of many possibleimplementations of a network that uses attributes to distribute content.

Referring to FIG. 3, system 300 for distributing content, according tovarious aspects of the present invention, includes fixed content servers310, 320, 324, 330, 334, 340, and 344. Content server 310 distributescontent to a region. Its geographic position may be anywhere, but itcommunicates with content servers 320 and 324. Content servers 320 and324 are children of content server 310. Communication between contentservers 310, 320, and 324 may be accomplished using any conventionalcommunication equipment and/or techniques.

Content server 320 distributes content to airport no. 1. It may begeographically positioned anywhere. Content server 320 communicates withcontent servers 340 and 344. Content servers 340 and 344 are children ofcontent server 320. Communication between content servers 320, 340, and344 may be accomplished using any conventional communication equipmentand/or techniques.

Content server 324 distributes content to airport no. 2. It may begeographically positioned anywhere. Content server 324 communicates withcontent servers 330 and 334. Content servers 330 and 334 are children ofcontent server 324. Communication between content servers 324, 330, and334 may be accomplished using any conventional communication equipmentand/or techniques.

Content servers 330, 334, 340, 344 communicate with nomadic contentservers on aircraft that arrive at gates of their respective concourses.Content server 340 and 344 are positioned at concourse no. 1 andconcourse no. 2 respectively of airport no. 1. Content server 330 and334 are positioned at concourse no. 1 and concourse no. 2 respectivelyof airport no. 2.

Each content server includes a set of attributes and a rule. A set ofattributes for a fixed and/or nomadic content server may include anyattribute discussed in Table 1 through Table 4. In this example, fixedcontent servers 310, 320, 324, 330, 334, 340, and 344 include attributesets 311, 321, 325, 331, 335, 341, and 345 respectively. Nomadic contentservers 350 and 360 include attribute sets 352 and 362 respectively.Insertion device 370 includes attribute set 372. Extraction device 390includes attribute set 392. Although attribute sets discussed above mayinclude any attribute from Table 1 through Table 4, the attributesdiscussed in this example are: airlines, aircraft, genre, and flight.

Each content server and extraction device 390 may further include arule. A rule for each content server and extraction device 390 mayinclude the properties and function of a rule as described above. A ruleis applied to attributes of a content server and a package item todetermine whether a content server should take an action with respect toa package item. An action may include accepting (e.g., receiving),storing, and/or forwarding a package item.

Rules 312, 322, 326, 332, 336, 342, 346, and 394 for this exampleperform a comparison (e.g., logical, character, binary, Boolean) betweeneach value of an attribute of a content server and each value of theattribute of a package item. A comparison that find a match (e.g., same,true, 1) indicates that the content server should receive the packageitem for forwarding to children content servers as discussed above. Acomparison that does not find a match indicates that the content servershould receive the package item for forwarding to the parent of thecontent server as discussed above.

For example, attribute set 311 includes the attribute “airline” havingthe values “A,” “B,” “X,” “Y,” and “Z.” Rule 312 specifies that eachvalue for the attribute “airline” of content server 310 should becompared to each value for the attribute “airline” of a package item. Amatch between a value of the content server “airline” attribute and avalue of the package item “airline” attribute indicates that the contentserver receive the package item for forwarding to children contentservers. Applying rule 312 using attribute 311 means that content server310 will take an action for any package item that should be received byan aircraft of airlines A, B, X, Y, or Z.

In another example, attribute set 352 of content server 350 includes theattribute “model” (e.g., aircraft model) having the value 747 and 737.Rule 354 for content server 350 has the operation “no match” for theattribute “model.” In this case, each value of the attribute “model” forcontent server 350 is compared with each value of the attribute “model”for a package item. In the event that the values of “model” for contentserver 350 do not match the values of “model” for a package item,content server 350 receives the package item. Because content server 350does not have children content servers, content server 350 will receivethe package item for its own use. Applying rule 354 using attribute 352means that content server 350 will take an action on all package itemsthat are not intended for aircraft model nos. 747 and 737.

As an example of distributing content, applying a rule, and taking anaction, suppose that content server 310 receives a package item and/or anotice of a package item having the attributes and attribute valuesshown in Table 5. The package item may have other attributes andattribute values in addition to those shown in Table 5, but for thisexample, the attributes of Table 5 are discussed to illustratedistribution of a package item. The attributes of Table 5 are alsoattributes of an airplane. A package item having the attribute values ofTable 5 is referred to herein as package item no. 1.

TABLE 5 Package Item No. 1 Attributes Attribute Name Description AirlineX Aircraft model 767, 777, A380, A350, A340.

Upon receiving package item no. 1 or a notice that package item no. 1 isavailable for receipt, content server 310 receives and/or requests theattributes for package item no. 1. Attributes for a package item may beseparate from or a part of the package item. In one implementation, theattributes of a package item are part (e.g., data field, meta data) ofthe package item, so the entire package item must be received to receivethe attributes of the package item.

Content server 310 uses rule 312 to determine whether it should receive,or in this case retain and not delete, package item no. 1. In thisexample, as discussed above, attribute set 311 for content server 310includes the attribute “airline” with the values A, B, X, Y, and Z.Content server 310 compares each value of attribute “airline” ofattribute 311 to each value of the attribute “airline” of the attributeof package item no. 1. The comparison results in a match between the Xvalue of attribute 311 and the X value of the attribute of package itemno. 1. Because a match occurs as a result of applying rule 312, contentserver 310 receives and stores, or retains and does not delete, packageitem no. 1.

Because attribute 311 of content server 310 includes the values for the“airline” attribute of its children content servers (320, 324, 330, 334,340, 344), at least one of its children will accept package item no. 1.As a result, content server 310 either sends package item no. 1 tocontent servers 320 and 324 or advises content servers 320 and 324 ofpackage item no. 1, so servers 320 and 324 may request package item no.1 or the attribute set of package item no. 1.

Content servers 320 and 324 perform a comparison between the values ofattributes 321 and 325 respectively and the values of attributes ofpackage item no. 1 as discussed above with respect to content server310. A match occurs for content server 320, so content server 320receives package item no. 1. A match does not occur for content server324, so content server 324 does not receive package item no. 1 or ifalready received, discards package item no. 1. Because attribute“airline” of attribute 325 includes the values of its children contentservers (e.g., 330, 333), if content server 324 does not detect a matchwhen applying rule 326, content server 324 knows that no child willdetect a match.

Because content server 320 detects a match when applying rule 322 toattribute 321 and the attribute of package item no. 1, content server320 receives package item no. 1 and forwards package item no. 1 or anotice of package item no. 1 to content servers 340 and 344. Contentserver 340 applies rule 342 to attribute 341 and the attribute ofpackage item no. 1 and detects a match, so content server 340 receivespackage item no. 1. Content server 344 applies rule 346 to attribute 345and attribute of package item no. 1, but does not detect a match, socontent server 344 does not receive or discards package item no. 1.

Content server 340 retains package item no. 1 for delivery to nomadicservers. Content server 340 may provide package item no. 1 to as manynomadic content servers that have matching attributes. Each nomadicserver applies its rule to its own attribute and the attribute ofpackage item no. 1 to determine if it should receive package item no. 1.In this case, nomadic server 350 detects a match while comparing thevalues of the “airline” attribute of attribute set 352 and the attributeset of package item no. 1. Nomadic server 350 also applies rule 354 toeach value of the “model” attribute for attribute set 352 and theattribute set for package item no. 1. The “model” attribute for packageitem no. 1 does not include the value “747” or “737,” so no match isfound between the nomadic content server attribute and package item no.1 attribute. Because rule 354 specifies “no match,” nomadic contentserver 350 receives package item no. 1 because applying rule 354 toattribute set 352 and the attribute set for package item no. 1 indicatesthat nomadic content server 350 should receive package item no. 1 upondetecting a match for “airline” and no match for “model.”

The lightning bolt symbol between content server 340 (344) and nomadiccontent server 350 (360) represents communication between the contentserver and the nomadic content server via a wireless communicationchannel.

Each server that has received a copy of package item no. 1 may retain acopy of package item no. 1. The value of attribute “expiration date”(not shown in Table 5) may provide a content server a time frame forretaining package item no. 1. In an implementation, a content serverretains package item no. 1 until the local time is greater than thevalue of the expiration date attribute. In another implementation, onlyfixed content servers that communicate with nomadic content serversretain package item 1 for delivery to nomadic content servers. Otherfixed contents servers that do not communicate with nomadic contentservers receive and forward package item no. 1, but do not retainpackage item no. 1 after it has successfully been forwarded.

In another example of distributing content, applying a rule, and takingan action, suppose that content server 310 receives a package itemand/or a notice of a package item having the attributes and attributevalues shown in Table 6. The package item may have other attributes andattribute values in addition to those shown in Table 6. A package itemhaving the attribute values of Table 6 is referred to herein as packageitem no. 2.

TABLE 6 Package Item No. 2 Attributes Attribute Name Description AirlineZ Flight no. 263

Upon receiving package item no. 2 or a notice that package item no. 2 isavailable for receipt, content server 310 receives and/or requests theattributes for package item no. 2. Content server 310 uses rule 312 todetermine whether it should receive package item no. 2. In this example,as discussed above, attribute set 311 for content server 310 includesthe attribute “airline” with the values A, B, X, Y, and Z. Contentserver 310 compares each value of attribute “airline” of attribute 311to each value of the attribute “airline” of package item no. 2. Thecomparison results in a match between the Z value of attribute 311 andthe Z value of the attribute of package item no. 2. Because a matchoccurred as a result of applying rule 312, content server receivespackage item no. 2.

Because attribute 311 of content server 310 includes the values for the“airline” attribute of its children content servers (320, 324, 330, 334,340, 344), at least one of its children will accept package item no. 2.As a result, content server 310 either sends package item no. 2 tocontent servers 320 and 324 or advises content servers 320 and 324 ofpackage item no. 2, so servers 320 and 324 may request package item no.2 or the attribute set of package item no. 2.

Content servers 320 and 324 perform a comparison between the values ofattributes 321 and 325 respectively and the values of attributes ofpackage item no. 2 as discussed above with respect to content server310. A match occurs for content server 320 and content server 324, socontent servers 320 and 324 receive package item no. 2.

Content server 320 forwards package item no. 2 or a notice of packageitem no. 2 to content servers 340 and 344. Content server 324 forwardspackage item no. 2 or a notice of package item no. 2 to content servers330 and 334.

Content server 340 applies rule 342 to attribute 341 and the attributeof package item no. 2, but does not detect a match, so content server340 does not receive package item no. 2.

Content server 344 applies rule 346 to attribute 345 and attribute ofpackage item no. 2. Content server 344 detects a match for the attribute“airline” because attribute 345 includes attribute “airline” with avalue of “Z” and package item no. 2 includes attribute “airline” with avalue of “Z.” Attribute set 345 does not include the attribute “flight,”so no comparison is made for the “flight” attribute of package item no.2. Content server 344 receives package item no. 2 based on the match forthe “airline” attribute.

Content server 330 applies rule 332 to attribute 331 and the attributeof package item no. 2, but does not detect a match, so content server330 does not receive package item no. 2.

Content server 334 applies rule 336 to attribute 335 and attribute ofpackage item no. 2. Content server 334 detects a match for the attribute“airline.” Attribute set 335 does not include the attribute “flight,” sono comparison is made for the “flight” attribute of package item no. 2.Content server 334 receives package item no. 2 based on the match forthe “airline” attribute.

Content servers 344 and 334 retain package item no. 2 for delivery tonomadic servers. Each nomadic server applies its rule to its ownattribute and the attribute of package item no. 2 to determine if itshould receive package item no. 2. In this case, nomadic server 360detects a match while comparing the values of the “airline” attribute ofattribute set 362 and the attribute set of package item no. 2. Nomadicserver 360 also applies rule 364 to each value of the “flight” attributefor attribute set 362 and the attribute set for package item no. 2. Thevalue of the “flight” attribute of attribute 362 matches the value ofthe “flight” attribute of package item no. 2, so nomadic server 360receives package item no. 2.

A flight number may be included as an attribute of a package item toprovide distribution of a package item to a nomadic content server of anairplane assigned the particular flight number. In this case, packageitem no. 2 appears to be intended for flight no. 263; however, packageitem no. 2 may be received by any content server that does not provide avalue for the “flight” attribute of its attribute set or that does notrequire a match of the “flight” attribute in its rule. Delivery of aparticular package item to a particular nomadic server to the exclusionof other nomadic servers may be accomplished by providing attributevalues for each nomadic content server that uniquely identify eachnomadic content server or the vehicle that carries the nomadic contentserver, such as airline, gate number, flight number, model number,and/or tail number. A rule may also be fashioned to detect package itemsfor a particular flight or aircraft.

Insertion device 370 provides content to network 300 for distribution.In this example, insertion device 370 is in an aircraft. A system (e.g.,electrical, hydraulic, oxygen, fuel, propulsion, navigation, flightcontrols, ice protection, emergency, in-flight entertainment, crew,credit card transaction data, frame stress transducers, black box, strutposition transducers) of the aircraft produces data. The data may beused to track maintenance, detect failures, assess crew performance,and/or measure system efficiency. Insertion device 370 may receive datafrom the systems of the aircraft and prepare the data for distributionvia network 300.

Insertion device 370 may prepare data for distribution by organizingdata into package items. Insertion device 370 may prepare a package itemfor distribution by preparing a set of attributes and assigningattribute values. A nomadic server of the aircraft may cooperate withthe insertion device to prepare data for distribution. An owner oroperator of the aircraft may be interested in receiving the data. Thedata may be provided by the aircraft and distributed through the networkto an extraction device owned by the owner or operator of the aircraft.Attributes may be assigned to the package item that contains data, sothat the package item is distributed to the extraction device.

In one implementation, insertion device 370 receives performance datafrom the aircraft engines. Insertion device 370 organizes the data intoone or more package items. Insertion device 370 retains the package itemuntil the aircraft arrives at a gate where insertion device 370 mayestablish communication (e.g., wireless) with fixed content server 334.Insertion device 370 is on an aircraft operated by airline “X,” soinsertion device 370 assigns the value “X” to the “airline” attribute ofthe attribute set 372 of the package item. Insertion device 370 alsoassigns the value “main” (e.g., maintenance) to the “genre” attribute toidentify the package item as containing maintenance data. For thisexample, the package item formed by insertion device 370 is referred toas package item no. 3 and includes the attributes provided in Table 7.The package item may have other attributes and attribute values inaddition to those shown in Table 7. In one implementation, all packageitems containing maintenance data are assigned at least the attributesshown in Table 7.

TABLE 7 Package Item No. 3 Attributes Attribute Name Description AirlineX Genre Main (maintenance)

Upon establishing communication with content server 334, insertiondevice 370 informs content server 334 that it has package item no. 3 fordistribution. Content server 334 receives the package items or a noticeof the package items and applies rule 336 to attribute set 335 andattribute set 372 of package item no. 3. In this case, content server334 does not detect a match for the “airline” attribute.

In the previous examples of distributing a package item, a contentserver did not accept a package item when a match did not result fromapplying the rule. The previous examples showed distribution from parentto child. In each of the above examples, content server 310 received apackage item (e.g., no. 1, no. 2). Because attribute set 311 includesthe attribute and attribute values for distributing to the childrencontent servers of content server 310, a resultant match from applyingrule 312 informs content server 310 that it or one of its childrenshould receive the package item. The same logic applies to contentservers 320, 324, 330, 334, 340, and 344. The attribute set of eachincluded attributes for distributing content to children contentservers, so a match indicates that the content server should receive thepackage item for distribution to children content servers.

When a child content server receives a package item, especially a childcontent server at a lower level of the parent-child hierarchy, the childcontent server does not know the attributes of its parent contentserver. Lacking knowledge of the attributes of its parent, a childcontent server forwards all package items that the child receivesindependent of its parent to its parent.

In this example, using rule 336 content server 334 does not detect amatch between attribute set 335 and attribute set 372. Lacking amatching result, content server 334 does not retain package item no. 3for distribution to other nomadic content servers. However, contentserver 334 receives package item no. 3 and forwards it to content server324. Content server 324 applies rule 326 to attribute set 325 andattribute set 372 and does not detect a match. Content server 324 doesnot retain package item no. 3, but forwards package item no. 3 tocontent server 310. Content server 310 applies rule 312 to attribute set311 and attribute set 372 and detects a match.

Because content server 310 detects a match, content server 310 storespackage item no. 3 for forwarding to its children servers. Becausecontent server 310 did not receive package item no. 3 from its parent,content server 310 also forwards package item no. 3 to its parent.

When content server 310 provides package item no. 3 or a notice ofpackage item no. 3 to extraction device 390, extraction device 390applies rule 394 to attribute set 392 and attribute set 372 of packageitem no. 3. Extraction device 390 finds a match for the “airline”attribute and for the “genre” attribute, so extraction device 390accepts package item no. 3. Extraction device 390 is located at theheadquarters for airlines “X,” “Y,” and “Z.” Headquarters desires toreceive maintenance data for the aircraft of its fleet. Extractiondevice 390 may be located at any place in the network or at any level ofthe parent-child hierarchy.

As discussed above, upon detecting a match, content server 310 providesthe package item or a notice of the package item to its children contentservers. In the case of package item no. 3, content server 310 willprovide package item no. 3 to content server 320 because it detected amatch. Content servers 320 and 340 will detect a match between theirrespective attribute sets (i.e., 321, 341) because the attributes setsand rules do not check for a match with the attribute “genre.” It isunlikely that any nomadic content server will use the data from packageitem no. 3; however, this example illustrates that the distribution of apackage may be controlled by the attribute set of a content server, theattribute set of a package item, and the rule applied by the contentserver to compare the attribute sets. A content server may includeattributes and rules that provide a no match result, so that the contentserver does not receive a package item. In this example, content server320 may use a rule that excludes receiving maintenance data from itsparent content server 310.

As discussed in the above examples, an attribute of a package item maynot be related to the type of content in a package item. The attributesfor package item nos. 1 and 2 include airline, aircraft model, andflight numbers. The attributes for package item nos. 1 and 2 do notinclude an attribute (e.g., package item type, genre) that providesinformation as to the type of content (e.g., video, audio, data) carriedby package item. Distribution in accordance with an attribute or a setof attributes may be accomplished without knowledge of the type ofcontent being distributed. An attribute may provide information as tothe purpose of the content, so distribution using an attribute mayinclude distribution in accordance with the purpose of the content.Attributes (e.g., airport, gate number, flight number) may result indistribution of a package item to a particular physical location. Aphysical location may not correspond to a geographic coordinate. Forexample, when distributing content by flight number, the physicallocation of where the content should be distributed may change if theorigin or destination of the flight number is change.

Depending on the attributes used to distribute content, content may bedistributed in accordance with the type of content (e.g., package itemtype, genre, package identifier, package item identifier), location of afixed and/or nomadic content server (e.g., content server area, airport,gate number, geographic coordinate, flight number), vehicle (e.g.,aircraft tail number, aircraft type, aircraft model, on-board systemidentifier), use of a vehicle (e.g., flight number, gate number, flightsegment/city pair), ability to use and/or need for content (e.g.,aircraft configuration, aircraft model, aircraft vendor, flight number,flight segment/city pair), vehicle owner (e.g., airline name, homeairport), package specific information (e.g., package identifier,package item identifier, package name), and/or time related information(e.g., activation date, delivery date, expiration date, date lastmodification).

A method for distributing content in a network may include method 400 ofFIG. 4. Distribution of content as discussed above may be accomplishedvia method 400. Method 400 may distribute package items in a networkincluding a network having a parent-child hierarchy. Method 400 mayinclude receiving notice of package item 410, detecting whether packageitem from child 412, detecting whether parent exits 414, sending noticeof package item to parent 416, marking to forward to parent 418,detecting whether package item new 420, receiving package item attributeset 422, detecting attribute match 424, sending notice of package itemto children 426, receiving package item 428, and detecting whethermarked for forwarding to parent 430.

In distributing package items, content servers communicate (e.g.,transmit, receive) information. Communication may occur between contentservers including a parent content server and one or more childrencontent servers. Information may include any data, signaling, control,and status communicated between content servers. For purposes of claritywhile discussing distribution, a content server, whether a parent or achild, that receives a package item is referred to as the receivingcontent server. A server that provides the package item is referred toas the providing content server. Any content server may perform the roleof a receiving or a providing content server. Process 400 may beperformed by a receiving content server.

Receiving notice of a package item may include receiving a notice of allpackage items retained (e.g., stored, held) by the providing contentserver, receiving a notice of package items not yet reported by theproviding content server, receiving a notice of package items receivesince the last notice, and/or receiving notice of a single package item.A notice may include information (e.g., data) regarding a package item.A notice may include attributes of a package item. A notice may includethe entire package item. A notice may identify each package itemuniquely (e.g., package identifier). A notice may be communicate in anyconventional (e.g., wired, wireless) manner using any conventionalcommunication protocol. In one implementation, receiving a notice 410includes receiving a list of package items retained by a providingcontent server, but not yet reported to a neighboring (e.g., parent,child) content server.

Detecting whether a notice of a package item has been received from achild includes receiving a communication via a channel dedicated tocommunication with a child server, receiving a identifier of the contentserver that sent the notice of a package item, and/or polling neighborcontent servers to determine which content server sent notice of apackage item. In one implementation, during initialization each childcontent server registers (e.g., checks-in) with the parent server andidentifies itself with each communication. A parent content server mayalso identify itself to a child server at initialization and/or witheach communication. In one implementation, detecting 412 is accomplishedby the receiving content server receiving notice of the identity of theproviding content server. A communications protocol may provideinformation as to the source of a communication (e.g., notice of packageitem) that may be used to detect whether a notice of a package itemcomes from a child content server.

Detecting whether a parent exits includes detecting whether thereceiving content server has a parent or is a content server at the topof the parent-child hierarchy that has not parent. As discussed above, achild server may register with its parent server at initializationand/or upon establishing communication. A content server may recordwhether it registered as a child with another content server and/orwhether other content servers registered with it as children. Detectingwhether a parent exits may be accomplished by a content server checkingits own records as to whether it has a parent content server. In animplementation, the receiving content server retains a record of itschildren and parent, so detecting 414 is accomplished by accessing therecord to determine if a parent exits.

If the receiving content server does not have a parent, the processmoves to detecting 420. If the receiving content server has a parent,the process moves to sending notice 416.

Sending a notice of a package item may include sending a notice of apackage item to neighbor content servers. A notice may include all orpart of the information provided in the notice received in receivingnotice of package items 410. Sending notice 416 is accomplished bysending a notice to the parent sever of a package item received from achild server.

Marking to forward to parent includes making an indication and/or recordthat a package item should be receive for forwarding to a parent.Marking may be a simple as setting a bit in a register and/or modifyinga header of a packet.

Detecting whether a package item is new may include comparing packageitems identified in a notice to package items previously considered by areceiving content server. Comparing may include comparing any aspect ofa package item to determine whether the receiving content server haspreviously received notice of the package item or the package itemitself. In one implementation, detecting 412 includes receiving a uniquepackage item identifier from the providing content server and comparingthe unique package item identifier to a list of package items previouslyconsidered by the receiving content server. Detecting 412 may furtherinclude recording the package item identifiers of all new package itemsto be able to identify them as not new afterwards.

Receiving a package item attribute set may include communicating arequest from the receiving content server to the providing contentserver. A receiving content server may request that a providing contentserver transfer one or more package item attribute sets to the receivingcontent server. The request may identify package items that thereceiving content server has detected are new to the receiving contentserver. Receiving a package item attribute set may include receivinginformation that includes the attribute set of a package item. Receivinga package item attribute set may include receiving an entire packageitem including the package item attribute set. As discussed above, apackage item and/or a package item attribute set may be communicated inany conventional manner. In one implementation of receiving package itemattribute set 422, the receiving content server sends a request to theproviding content server that identifies the attribute sets thereceiving content server would like to receive from the providingcontent server. A request to send an attribute set may identify thechannel (e.g., frequency, encoding, unicast, multicast) that theproviding content server may use to communicate the attribute set.

Upon receiving an attribute set, a receiving content server may detect(e.g., determine, compare) whether the attribute set matches (e.g.,corresponds, relates) to a package item of interest to the receivingcontent server. Detecting an attribute match may be accomplished asdiscussed above. Detecting a match may include applying a rule to anattribute set of the receiving content server and the attribute set ofthe package item as discussed above.

In an implementation of detecting attribute match 424, the attribute setof the receiving content server (“CS”) is compared to the attribute setof the package item (“PI”) in accordance with the Boolean expressionprovided below. In the Boolean expression, the symbol “==” means equalto, the symbol “!=” means does not equal, and the symbol “<” means lessthan. The result (e.g., output) of the Boolean expression, Match, istrue (e.g., 1) upon detecting a match and is false (e.g., 0) upondetecting that no match exists.

-   -   Match=(CS airline==PI airline) and        -   (CS aircraft model==PI aircraft model) and        -   (CS flight no.==PI flight no.) and        -   [(CS unfinished package ID==PI ID) and        -   (CS missing chunk no.==PI chunk no.)] and        -   (today's date<PI delivery deadline)

In the case of the above formula, the output Match becomes true when allBoolean expressions are true. A Boolean expression, for example, CSairline==PI airline, is true when the value of the attribute for thecontent server and the value of the attribute for the package itemproduce a true result in accordance with the Boolean expression. Forexample, when the value of the attribute CS airline is the same as thevalue of the attribute PI airline, the Boolean expression CS airline==PIairline is true. When the value of the attribute “today's date” is lessthan the value of the attribute PI delivery deadline, the Booleanexpression today's date<PI delivery deadline is true.

Sending a notice of a package item 426 may be accomplished in the samemanner as sending notice 416 discussed above except that the notice issent to content servers that are children of the receiving contentserver as opposed to the parent.

Receiving a package item may include a receiving content serverreceiving data using any conventional communication protocol via anyconventional medium. Receiving a package item may include a receivingcontent server providing a request to a providing content server to sendone or more package items to the receiving content server. A request mayidentify a channel that the providing content server may use to provide(e.g., transfer, communicate, transmit) the requested package items. Inthe event that the entire package item was sent with the attribute set,the receiving content server need not provide a notice of the packageitems for which a match was found because the receiving content serverhas already received the package items and may merely discard thepackage items for which there was no match. In one implementation,receiving a package item 416 includes providing a notice to theproviding content server to send one or more package items.

Detecting whether a mark has been recorded to forward a package item toa parent includes detecting and/or interpreting the record created bymarking 418. When a parent does not exist, process 418 is not executed,so a record is not created to mark that a package item should beforwarded to a parent. The absence of a record indicates that a packageitem should not be received for forwarding to a parent. If a parentexists, a record is created, so existence of a record indicates that apackage item should be received for forwarding to the parent. In animplementation, marking 418 is accomplished by setting a bit in aregister and/or setting a variable to a value. Detecting 430 isaccomplished by detecting the set bit in the register and/or detecting avalue of a register.

If detecting 430 detects the mark, process 428 is executed to receivethe package item. If a mark is detected, a notice has already been sentto the parent by sending 416, so the receiving content server receivesthe package item to have possession of it when the parent responds toreceiving the notice from process 416.

Another method for distributing content in a network may include method500 of FIG. 5. Method 500 may include requesting notice of package items510, detecting whether package item from child 512, detecting whetherparent exits 514, marking to receive for parent 516, detecting whetherpackage item new 518, receiving package item attribute set 520,detecting attribute match 522, receiving package item 524, and detectingwhether marked to receive for parent 526.

Processes detecting whether package item from child 512, detectingwhether parent exits 514, marking to receive for parent 516, detectingwhether package item new 518, receiving package item attribute set 520,detecting attribute match 522, receiving package item 524, and detectingwhether marked to receive for parent 528 may perform the functions andaccomplish the results of detecting whether package item from child 412,detecting whether parent exits 414, marking to forward to parent 418,detecting whether package item new 420, receiving package item attributeset 422, detecting attribute match 424, receiving package item 428, anddetecting whether marked for forwarding to parent 430 respectively asdiscussed above. Process 500 may be performed by a receiving contentserver.

A receiving content server may send a request to a neighbor contentserver to request that the neighbor content server provide a notice ofthe package items in possession of the neighbor content server. A noticeof package items sent responsive to a request may be the same or similarto the notice provided by process 410. Requesting a notice may includereceiving a notice responsive to the request. In an implementation,requesting 510 communicates a request to at least one neighbor contentserver for the neighbor content server to provide a notice of all of thepackage items stored by the neighbor content server. A notice mayinclude an attribute set for each package item and/or an entire packageitem. A neighbor content server may include a parent and/or a child.

A request may identify a time of a previous request to enable theneighbor (e.g., providing) content server to provide information aboutpackage items received after any previous request. A request may includean attribute set and rule from the receiving content server so that theproviding content server may provide a notice that identifies packageitems that may be of interest to the receiving content server.

A content server may retain a package item until it has responded to arequest from each neighbor content server.

A comparison of method 400 and method 500 shows that a receiving contentserver performing method 400 respond to notices sent to it from othercontent servers. Neighbor content servers push (e.g., provide) notices,without prior solicitation, to a receiving content server regarding thepackage items held by the providing content server. Receiving contentservers performing method 500 request information from neighboringcontent servers about package items held by neighbor content servers. Areceiving content server that performs method 500 pulls (e.g., requests)information from neighboring content servers and acts on the informationreceived responsive to its request.

A method of distributing information in a network may use method 400,method 500, or a combination of methods 400 and 500 to push and pullinformation about content throughout the network. The process ofdistributing package items throughout a network may be referred to ascontent inventory exchange.

In an implementation, content is routed through a network of fixedcontent servers. Each fixed content server retains content of interestto the nomadic content servers that that the fixed content server willat some time service. The attribute set of a fixed content server thatservices nomadic content servers is configured to receive the contentfor the nomadic content servers that will connect with the fixed contentserver. Knowledge of which nomadic content servers will at some timeconnect with a fixed content server may be provided by a schedule of theroute of the nomadic content servers. A fixed content server may servicenomadic content servers having common attributes and/or attributevalues, so the attribute set of the fixed content server may beconfigured to receive content for the common attributes and/or attributevalues.

A fixed content server may retain package items until the contentexpiration date is reached. After the content expiration date is past,the fixed server no longer stores the expired package items.

Upon arrival of a nomadic content server, the fixed content server, inthe role of a providing content server, provides a notice to the nomadiccontent server of the content held by the fixed content server. Thenomadic content server, in the role of a receiving content server,performs method 400 to determine whether the nomadic content serverwishes to receive content from the fixed content server. In anotherimplementation, the nomadic content server, in the role of receivingcontent server, performs method 500 and requests content from the fixedcontent server, which performs the role of the providing content server.

After the nomadic content server receives as much content as it can fromthe fixed content server during the duration of the connection betweenthe fixed and nomadic content servers, the nomadic contents serverleaves the communication range of the fixed content server and moves torepeat the process with a different fixed content server located at adifferent geographic location. A nomadic content server may also providecontent to the fixed content server during the duration of a connection.For example, maintenance information as discussed above may betransferred from the nomadic content server to the fixed content server.

Distribution of content is not limited to transfers between fixedcontent servers or fixed content servers and nomadic content servers. Anomadic content server may establish a connection with another nomadiccontent server for transfer of package items in accordance withattributes. A nomadic content server may establish a connection with afixed content server and another nomadic content server at the sametime. A nomadic content server may receive content from a fixed contentserver and provide the content received to another nomadic contentserver. Nomadic content servers may communicate with each other when oneor more of the nomadic content servers are outside the range ofcommunication of a fixed content server (e.g., at airport, but out ofrange, in-flight).

Nomadic content servers may communicate content between each other usingmethod 400 and/or method 500 as discussed above.

Content may be provided (e.g., inserted, injected) to a network fordistribution in accordance with attributes of the content. Insertion ofcontent into a network is discussed above with respect to insertiondevice 270, 272, and 370. Content may be inserted into a network to anycontent server, whether fixed or nomadic, in the hierarchy of thenetwork. A device (e.g., server, computer) that provides content to anetwork does not need to be a content server in the network. A devicethat inserts content may be external to the network. A device mayprovide content to a content server of the network.

A connection, whether wired or wireless, between a device that providescontent and a content server of the network may be referred to as aninsertion point. An insertion point may define an interface between asystem that is external to the network and a system that is internal toa network. An insertion point may be established using any conventionalcommunication and/or file transfer protocol. An insertion point may beestablished over any conventional medium including wired and/or wirelessnetworks.

A device that provides content to a network and/or a content server of anetwork may be referred to as an external content server.

Attributes may be assigned to content by a system that is whollyexternal to the network, wholly internal to the network, or that isdistributed between an external device and an internal device. Systems600, 700, and 800 respectively show systems that are wholly external,wholly internal, and both internal and external for assigning attributesto content and forming package items.

System 600 includes insertion device 610 and content server 690.Insertion device 610 includes content generator 620, attribute generator630, package item generator 640, package item queue 650, and contentserver emulator 660. Insertion device 610 communicates with contentserver 690 via connection 670, so connection 670 represents theinsertion point. Because content server 690 is part of the network, line680 represents the line between the external system (610) and internalsystem (690).

A content generator provides content. Content may include video, music,data, and/or interactive content. Content may be saved in anyconventional electronic file format. A content generator may include anyconventional system that generates electronic content.

In an implementation, content generator generates video and audiocontent for use in-flight use on airplanes. Content provided by acontent generator may include descriptors of the type of content for useby an attribute generator in generating a set of attributes or valuesfor an attribute.

For example, content generator 620 may include a description as towhether the content is video, music, or data. Video may be furtherclassified as feature length film, short film, commercials, news,sports, infomercial, television programming, weather, foreignprogramming, or any other classifier that describes the video. Music maybe classified as to type, such as, classical, modern, country, jazz,contemporary, new age, or any other type of classifier that describesthe music. Data may be classified as interactive shopping, computergame, news, books, magazines, short stories, interest stories, stillimages, or any other type of classifier that describes data. A contentgenerator may further provide information about the content, such aspresentation duration, file format, file size, creation date, contentcreator, and/or content requester.

An attribute generator provides an attribute set for content. A set ofattributes generated by an attribute generator may include theattributes for a package item as discussed above. An attribute generatormay cooperate with a content generator to provide an attribute set forcontent provided by the content generator. An attribute generator mayreceive information from any source to generate a suitable set ofattributes and/or attribute values for content. An attribute generatormay receive information from a manager of a network and/or a schedulerof vehicles (e.g., nomadic content servers) to aid in generating a setof attributes. Generation of an attribute set may include informationprovided by or selected by a human operator of an insertion device.

An attribute set may include a description of the content. For example,a value of the attribute package item description as discussed in Table3 may be set to indicate whether the content is video, music, data, orany other conventional type of data. The value of the attribute genre asdiscussed in Table 3 may be set to classify the type of video, music, ordata as discussed above.

In an implementation related to airlines, an external content providerreceives requests from airlines for content. A request from an airlinemay be used to generate the content and the attributes of the content.For example, an airline request may include the type of content, adeadline for delivering the content, and an expiration date for thecontent. A request may further include information related to or a valuefor any attribute discussed above for a package item. An externalcontent provide may further receive flight schedules, type of contentneeded per flight, departure airports, departure gates, gateinformation, delay information contents server geographic locations,information about communication capabilities between content servers,airports, gates or other physical locations from airlines, airportauthorities, and/or network managers. An attribute generator receivesthe information provided by the various sources and information aboutthe content and provides a set of attributes as discussed above.

A package item generator produces package items (or packages) fordistribution in a network that distributes data in accordance withattributes. A package item generator may combine content provided by acontent generator with an attribute set from an attribute generator thatis associated with the content. A package item generator may provide apackage item for distribution. A package item includes the attributesand characteristics of a package item as discussed above. A package itemgenerator my split content into may package items having an attributeset that permits reassembly (e.g., package item sequence number) by areceiving content server. A package item generator may provideindividual package items or a package of many package items.

In an implementation, package item generator 640 receive content fromcontent generator 620 and attribute sets from attribute generator 630 toform package items for distribution by a network that distributescontent using attributes as discussed above. A package item may be anelectronic file having the format and information discussed above.

A package item queue stores package items prior to insertion into thenetwork. A package item queue may receive and/or provide package itemsin any order. A package item queue may reorder (e.g., sort, arrange)package items in accordance with an attribute and/or a value of anattribute. A package item queue may provide package items as reordered.In an implementation, package item queue 640 is a first-in-first-outqueue.

A content server emulator emulates the functions and operations of acontent server as discussed above. A content server emulator may operatein accordance with the distribution protocol (e.g., method 400, method500) used by content servers of the network. In the case of an externaldevice that provides content to a network, the content server emulatorprovides package items to, but does not receive package items from, thenetwork and/or a content server of the network. In an implementation,content server emulator 660 functions as a providing content server forproviding content to a receiving content server as discussed above.Content server emulator 660 receives package items from package itemqueue 650 and provides the package items to content server 690 viainsertion point 670 in accordance with the content distribution protocolused in the network.

Content server emulator 660 may perform the functions of contentgenerator 620, attribute generator 630, package item generator 640, andpackage item queue 650.

System 700 includes insertion device 710 and insertion server 720.Insertion device 710 includes content generator 712, directoryclassifiers 716, external server 714, directory indicators 718, andoperator 719. Insertion server 720 includes directory 722, directory724, directory 726, attribute set generator 728, package item generator730, and content server emulator 770. Insertion server 720 may furtherinclude a package item queue (not shown), as discussed above, to bufferpackage items provided by package item generator 730 and received bycontent server emulator 770. Insertion device 710 communicates withinsertion server 720 via connection 750, so connection 750 representsthe insertion point. Because insertion server 720 is part of thenetwork, line 760 represents the line between the external system (710)and internal system (720, 780).

Content generator 712 performs the functions discussed above withrespect to a content generator. An external server may perform thefunctions of a content generator.

A directory classifier provides information about the type of contentthat each directory 722-726 may receive. For example, a directoryclassifier may specify that all content transferred to directory 722 becontent that is for Delta Airlines for use in domestic in-flightentertainment. Another directory classifier may specify that all contenttransferred to directory 724 be for United Airlines for internationalflights. Another directory classifier may specify that all contenttransferred to directory 726 be flight information for the flight crewof a particular flight, a particular type of aircraft, and/or aparticular airline.

A directory classifier may include information as to the insertion pointthat must be used to insert content into a directory. Each directory mayhave a unique address for accessing the directory. A directoryclassifier may include the information that an external server may needto access the directory. For example, information needed to access adirectory may include a directory name, directory number, an IP address,a file transfer protocol (“FTP”) address, a channel address, and/or anyconventional information for transferring information to a specificlocation and/or file system.

Information in a directory classifier may be provided to an insertiondevice by the entity (e.g., network manager, system operator)responsible for establishing directories in an insertion server.

A directory indicator indicates the directory to which a particularcontent must be provided. An operator may assist in forming a directoryindicator. An operator may assess the type of content, determine thedirectory most appropriate for the content in accordance with thedirectory classifiers, and provide the information for accessing theselected directory as a directory indicator. A directory indicator mayprovide an insertion server with instructions for accessing andtransferring content to a particular directory. An operator may includea human operator and/or a machine assisted by a human operator.

A directory indicator may be stored with the content or stored separatefrom the content (e.g., separate queue), but associated with the contentfor provision to the external server. In an implementation, a humanoperator assesses directory classifiers 716 and provides directoryindicator 718 for each file of content generated by content generator712. Directory indicator 718 is stored as metadata to each file ofcontent.

An external server receives content from a content generator anddirectory indicators. Using the directory indicator, the external servertransfers the content associated with the directory indicator to theappropriate directory in the insertion server. A content server mayperform any conventional communication and/or file transfer operation totransfer content to a directory. In an implementation, content server714 does not establish or manage directories 722-726. Content server 714receives content from content generator 712 and instructions on how totransfer the content to a directory from directory indicators 718.External server 714 transfers the content to a directory using theinstructions. In an implementation, external server 714 transferscontent to directories using FTP. Directory indicators 718 provideinstructions for transferring content using FTP. External server 714 haswrite-only access to directories 722-726.

A directory is a storage area that receives, stores, and providescontent. A directory is created, managed, and/or deleted by a manager ofthe insertion server and/or a network. A manager of the insertion servercreates directories and provides directory classifiers to externalproviders of content for use by an insertion device. A manager mayfurther specify the insertion point for transferring content frominsertion device 710 to directories 722-726 as discussed above.

An attribute generator provides attributes for distribution of packageitems in a network. An attribute generator provides an attribute thatcorresponds to the directory classifiers used by an insertion device totransfer content to a directory. An attribute generator has knowledge ofdirectory classifiers and/or of the directory structure so that ascontent is received from a directory, the attribute generator providesan appropriate attribute set for the content from the directory. Anattribute set provided by an attribute generator may include any of theattributes discussed above with respect to a package item.

Package item generator 730 may inform attribute generator 728 of thedirectory accessed to retrieve content to form a package item. Attributegenerator 728 provides an attribute set associated with the directoryaccessed to retrieve content. For example, each time package itemgenerator 730 accesses directory 724 to receive content to form apackage item, package item generator 730 requests attribute generator728 to provide the attribute set associated with directory 724.

A manager of the insertion server and/or the network provides theattribute set that corresponds to each directory. Because the managerprovides the directory classifiers, instructions for transferring to adirectory, creates the directories, and provides the attribute setassociated with each directory, the manager, for the most part, controlsthe process of inserting content into the network. An external contentprovider may improperly construe the directory classifiers and placeinappropriate content into a directory; however, directory classifiersare generally so simple, as discussed above, that an external providemay construe them without error.

Package item generator 730 may perform some or all of the functions of apackage item generator discussed above. Package item generator 730 mayreceive content from a directory, an attribute set from attributegenerator 728 and provide package items for distribution in a network.

In an implementation, attribute generator 728 provides an attribute setfor content stored in directory 722 that was transferred to directory722 in accordance with the content classifier indicating that thecontent is for Delta Airlines for use for domestic in-flightentertainment. Each time package item generator 730 receives contentfrom directory 722, attribute generator 728 provides an attribute setappropriate for the content. In this example, the attribute set mayinclude a package identifier, a package item sequence number, an airlinename with the value Delta, an activation date, a delivery date, anexpiration date, and airport having values that correspond to theairports that originate domestic flights for Delta Airlines.

Content server emulator 770 may perform the functions of a contentserver emulator discussed above. The functions of content serveremulator 770 may be performed by a content server of a network.

All or a portion of the functions of insertion server 720 may be performby a content server of a network (e.g., server 780). For example,insertion server 720 may be part of a fixed content server or a nomadiccontent server. In an implementation, insertion server 720 is located onan airplane, so that maintenance information from the plane may beinserted into the network via the nomadic content server on the planefor distribution to the plane owner or airline operator.

System 800 includes insertion device 810 and insertion server 820.Insertion device 810 includes content generator 812, abbreviatedattribute generator 814, external server 816, and operator 818.Insertion server 820 includes directory 824, directory 840, attributeselect 860, content select 862, complete attribute generator 870,package item generator 880, and content server emulator 890. Insertionserver 820 may further include a package item queue (not shown), asdiscussed above, to buffer package items provided by package itemgenerator 880 and received by content server emulator 890. Insertiondevice 810 communicates with insertion server 820 via connection 850, soconnection 850 represents the insertion point. Because insertion server820 is part of the network, line 852 represents the line between theexternal system (810) and internal system (820, 892).

Content generator 812 performs the functions discussed above withrespect to a content generator.

An abbreviated attribute generator provides a set of attributes having avalue for some or all of the attributes and/or some or all of the valuesfor the attributes. The attribute set may be a subset or the entirety ofthe attribute set used to distribute content in a network. Anabbreviated attribute generator provides an attribute set and values forattributes in accordance with the content provided by a contentgenerator. An operator may provide information about the content to theabbreviated attribute generator, so that the abbreviated attributegenerator may generate an appropriate set of attributes. Operator 718may include an electronic device that receives a description of thecontent from content generator 812, as discussed above, for use byabbreviated content generator 814 to produce a set of attributes.Operatory 718 may include a human operator that receives informationregarding content from content generator 812 or another source andprovides information to abbreviated attribute generator 814 forgeneration of an attribute set.

For example, content generator 812 may receive information, likely froma human operator, that the content being generated is for AmericanAirlines eastbound domestic flights. Content generator 812 may includethe information from the human operator into the content file asmetadata. Because the information necessary to produce the abbreviatedattribute has been embedded into the content file, operator 818 includesan electrode device for receiving the metadata and providing themetadata to abbreviated attribute generator 814. Abbreviated attributegenerator 814 uses the metadata to produce an abbreviated set ofattributes and provides the set of attributes to external server 816.

External server 816 receives content from content generator 812 and anabbreviated set of attributes from abbreviated attribute generator 814.External server 814 transfers the content and the abbreviated attributeset to insertion server 820. External server 814 transfers content andabbreviated attributes to directories in a storage system of insertionserver 820. In this example, external server 816 controls the creation,deletion, and maintenance of directories in insertion server 820.External server 816 may use any criteria for creating a directory fortransfer of content. For example, external server 816 may create onedirectory for each airline, one directory for all domestic flightsregardless of airline, one directory for each airport, and/or onedirectory for each gate at each airport. External server 816 createsdirectories in accordance with its policy and transfers content andabbreviated attribute sets to the directories in accordance with thepolicy.

A manager of the insertion server or network may provide external server816 with information for accessing and managing directories in insertionserver 820. For example, a manager may provide a directory namingpolicy, a maximum amount of storage space, an IP address, an FTPaddress, instructions for accessing (e.g., read, write, delete) thestorage space, and/or any information for transferring information to aspecific location and/or file system using a conventional protocol.

Because insertion device 810 provides content with an abbreviatedattribute set, insertion server 820 does not need to have knowledge ofthe criteria for creating each directory 822 or 840. An abbreviatedattribute (e.g., 826, 832) provides enough information for insertionserver 820 to complete the attribute set if necessary.

An external server may perform the functions of a content generator andan abbreviated attribute generator. An external server may perform someor all of the functions performed by an electronic operator. An externalserver may include a user interface (e.g., keyboard, monitor, software)for receiving information from and providing information to a humanoperator.

In an implementation, external server 816 users FTP to create and managedirectories and to transfer data into the directories in the storagesystem of insertion server 820. External server 816 uses FTP operationsto create directories 822 and 840. Using an FTP write command, externalserver 816 transfers content 828 and abbreviated attribute set 826 intodirectory 822 as file 824, and content 834 and abbreviated attribute set832 into directory 822 as file 830. External server 816 may also createand transfer files to directory 840 or any other directory externalserver 816 creates. In this example, external server 816 createsdirectory 822 to hold content for Alaskan Airlines flights. File 824 mayhold a movie. File 830 may hold music. Directory 840 may be created tohold content using a different criteria.

An attribute selector receives abbreviated attributes from files storedin a directory in any conventional manner. A content selector receivescontent from files stored in a directory in any conventional manner.

A complete attribute generator receives an abbreviated attribute set andaugments the attribute set to form a complete attribute set fordistributing content in a network. A complete attribute generator mayadd attributes and/or provide values for attributes to a set ofattributes provided by abbreviated attribute generator 814. A completeattribute generator may receive information from a manager of a networkfor forming a complete attribute set in accordance with an abbreviatedattribute set.

In the event that abbreviated attribute generator 814 provides acomplete attribute set, complete attribute generator 870 may perform thefunction of verifying the structure and content of the attribute set andflagging any potential issues as opposed to providing additionalattributes and/or values. An abbreviated attribute generator may providea complete attribute set in the manner discussed above with respect tosystem 600. In a system in which abbreviated attribute generator 814provides a complete set of attributes and no verification is needed,complete attribute generator 870 may be eliminated from insertion server820.

Package item generator 880 may perform some or all of the functions of apackage item generator discussed above. Package item generator 880receives content from content select 862 and the complete attribute setassociated with the content from complete attribute generator 870 togenerate a package item.

Content emulator 890 may perform some or all of the functions of acontent emulator discussed above. A content emulator receives packageitems from package item generator 880 for distribution in the network.Content emulator 890 may provide package items to content server 892.

As discussed above, the functions of a content emulator may be performedby a content server of the network. As further discussed above, thefunctions of an insertion server may be performed by a content server.The memory of a content server may be used as a storage area forestablishing directories. A content server may cooperate with anexternal server to create and manage directories as instructed by thecontent server. A content server may perform the functions of attributeselect 860, content select 862, complete attribute generator 870, andpackage item generator 880.

Content may be received (e.g., extracted, removed) from a network inaccordance with attributes of the content. Extraction of content isdiscussed above with respect to extraction device 278 and 390. Contentmay be extracted from a network from any content server in the hierarchyof the network. A device (e.g., server, computer) that extracts contentfrom a network does not need to be a content server in the network. Adevice that extracts content may be external to the network. A devicemay cooperate with a content server of the network to extract contentfrom the network in accordance with a set of attributes.

A connection, whether wired or wireless, between a device that extractscontent and a content server of the network may be referred to as anextraction point. An extract point may define an interface between asystem that is external to the network and a system that is internal toa network. An extraction point may be established using any conventionalcommunication and/or file transfer protocol. An extract point may beestablished over any conventional medium including wired and/or wirelessnetworks.

System 900 extracts content from a network that distributes content inaccordance with attributes. System 900 includes extraction server 910and extraction device 950. Extraction server 910 includes content server920 and transfer device 940. Content server 920 includes attributes 922.Transfer device 930 includes directory generator 932, directory queue934, content queue 936, and transfer server 938. Extraction device 950includes directory 952, directory 954, directory 956, and externalserver 958. Extraction server 910 communicates with extraction device750 via connection 940, so connection 940 represents the extractionpoint. Because extraction server 910 is part of the network, line 942represents the line between the internal system (910) and the externalsystem (950).

An extraction server receives content from a network that distributescontent in accordance with attributes. An extraction server providescontent to an extraction device. An extraction server may communicatewith an extraction device using any conventional communication and/orfile transfer protocol. An extraction server may transfer content to anextraction device using any conventional medium (e.g., wired, wireless,network, direct connection).

An extraction device is a device (e.g., computer, server) that isexternal to the network. A manager of an extraction device may provide amanager of the network with a description of the data the extractiondevice would like to receive. A network manager may use the descriptionto form an attribute set of a content server for receiving the desiredcontent. Upon receipt of content, the extraction server may transfer theinformation to the extraction device. An extraction device may usecontent extracted from the network for any purpose.

An extraction server may transfer content to an extraction device via anextraction point. An extraction point includes any conventionalconnection for transferring information.

In an implementation, content server 920 performs the functions of acontent server of a network that distributes content in accordance withattributes. Content server 920 may be a fixed content server or anomadic content server. Content server 920 may perform the functions ofa parent and/or a child content server. A fixed content server thatperforms the functions of an extraction server may extract content froma network for provision to a geographically fixed location. For example,a fixed content server may extract airplane maintenance informationinserted into the network by airplanes at any location in the network.The maintenance information would be distributed via the network to thefixed content server that extracts the maintenance content for provisionto the offices of the airline or airplane owner.

A nomadic content server that performs the functions of an extractionpoint may extract content from a network for use by the nomadic vehicleor the personnel of the nomadic vehicle. For example, a nomadic contentserver on an aircraft may receive content for the in-flightentertainment system of the aircraft. Upon receipt of the content, thenomadic server on the aircraft may transfer the entertainment content tothe in-flight entertainment system for use by passengers in the plane.

Content server 920 includes at least one set of attributes for receivingthe content desired by the extraction device. A manager of extractiondevice 950 provides a manager of content server 920 or the network witha description of the characteristics of the information to betransferred to extraction device 950. The manager of content server 920generates (e.g., develops, creates, configures) one or more sets ofattributes 922 for use by contents server 920. Using attributes 920,content server 920 receives the information that extraction device 950desires to receive.

For example, an airline (e.g., Southwest) may desire to receiveinformation from each crew of its aircraft for each flight. Suchinformation may include the name of the crew on the flight, thefunctions perform by each crew member, and reportable incidents (e.g.,passenger illness, passenger unruliness, food shortages, food surpluses,directives from the captain, crew illness, technical difficulties withequipment) detected by crew members. A manager of content server 920would develop an attribute set, as described above, that would permitcontent server 920 to receive all crew information for all Southwestflights. A set of attributes may be developed so that content server 920receives content having other attributes (e.g., maintenance data,aircraft system data, fuel consumption data, take-off times, touch-downtimes, weight).

An extraction device may set aside storage for receipt of content froman extraction server. An extraction device may provide instructions fortransferring content to the storage area of the extraction device. Anextraction device may provide information (e.g., IP address, FTPaddress, conventional transfer protocol information) for establishing aextraction point.

In an implementation, extraction device 950 and/or a manager ofextraction device 950 creates directories 952, 954, and 956 forreceiving content from extraction server 910. Extraction device 950specifies the attributes of the content for each directory. Extractiondevice 950, or a manager of extraction device 950, provides thedirectory information to a manager of extraction server 910. The managerof extraction server 910 associates the attributes specified forreceiving content at content server 910 with the directories created bycontent server 950. The association information is incorporated intodirectory generator 932.

A directory generator translates a set of attributes used to receivecontent into information for transferring the content into a directoryof extraction device 950. The information used for transferring contentmay include a directory name, a directory location, an IP address, anFTP address, or any information for transferring data using aconventional communication and/or file transfer protocol. A transferserver uses the information provided by directory generator 932 totransfer content to an appropriate directory in extraction device 950.

Content queue 936 performs the functions of a content queue discussedabove. Directory queue 934 queues directory information provided bydirectory generator 934. Content queue 936 and directory queue 934cooperate to provide the directory information that is associated withthe proper content.

A transfer server receives content and directory information. A transferserver transfers the content to the directory indicated by the directoryinformation. A transfer server may use any conventional communicationand/or file transfer protocol to transfer information to a directory ofextraction device 950. In an implementation, transfer system 938receives content from content queue 936 and directory information fromdirectory queue 934. Transfer server 938 uses the directory informationto transfer the associated content to a directory (e.g., 952, 954, 956)of extraction device 950. The directory information from directory queue934 enables transfer server 938 to transfer content to a directoryestablished to receive content having the attributes of the contenttransferred.

For example, extraction device 950 may be operated by United airlines.United airlines may wish to receive maintenance information from eachaircraft after each leg of a flight, crew information, usage ofin-flight paid services, time of arrival information, departure timeinformation, and food and beverage consumption information. A manager ofthe United extraction device provides a description of the content thatUnited wishes to receive, a description of the directories establishedto receive the content, and instructions on how to access thedirectories. The manager of content server 920 develops one or more setsof attributes so that content server 920 will receive the contentdesired by United. The manager of the systems on each United aircraftconfigures the systems of the aircraft to provide the desired content toan insertion device on the aircraft. The insertion device will provide aset of attributes for the desired content so that the content may bedistributed through the network in accordance with the attributes andreceived by content server 920. The manger of the nomadic content serveron each United aircraft configures the nomadic content server on eachaircraft to receive the content inserted into the network by theaircraft insertion device.

As an aircraft operates, the systems on the aircraft provide informationto the insertion device on the aircraft. The insertion device cooperateswith the nomadic content server, which performs the functions of aninsertion server discussed above, to provide a set of attributes for thecontent. The nomadic content server receives the content from theinsertion device and forms package items. Upon touch-down at an airport,the nomadic contents server transfers the package items to a fixedcontent server at the airport where the aircraft is presently located.The package items are distributed through the network in accordance withthe attributes of each package item. Content server 920 receives thepackage items in accordance with the one or more sets of attributes ofcontent server 920. Content server 920 transfers the content to anappropriate directory in extraction device 950 as discussed above.

External server 958 may access the directories 952-956 to retrieve thecontent. External server 958 may transfer content to any person and/orsystem using any conventional protocol. External server 958 may provideinformation (e.g., amount transferred, amount retrieved, errors, storageavailable, transfer rates, statistics therefor) regarding the contenttransferred to directories of extraction device 950. External server 958may further be used to manage the directories of extraction device 950.

A content server may perform all of part of the functions of a transferdevice.

The foregoing description discusses preferred embodiments of the presentinvention, which may be changed or modified without departing from thescope of the present invention as defined in the claims. Examples listedin parentheses may be used in the alternative or in any practicalcombination. As used in the specification and claims, the words‘comprising’, ‘including’, and ‘having’ introduce an open endedstatement of component structures and/or functions. In the specificationand claims, the words ‘a’ and ‘an’ are used as indefinite articlesmeaning ‘one or more’. While for the sake of clarity of description,several specific embodiments of the invention have been described, thescope of the invention is intended to be measured by the claims as setforth below.

What is claimed is:
 1. A system comprising: a fixed content serverpositioned at a location, the fixed content server comprising aprocessing circuit configured to: store electronic content for deliveryto nomadic servers on vehicles; obtain information defining a schedulefor arrival of an identified one of the vehicles transporting a nomadicserver to a sequence of destination locations; identify destinationcontent servers at respective ones of the sequence of destinationlocations; generate electronic packages containing portions of theelectronic content; initiate communication delivery of a first one ofthe electronic packages from the fixed content server to a firstdestination content server at a first one of the sequence of destinationlocations based on the schedule for arrival of the identified vehicletransporting the nomadic server to the first one of the sequence ofdestination locations so delivery of the first one of the electronicpackages is initiated while the identified vehicle is traveling to thefirst one of the sequence of destination locations and then uploadedfrom the first destination content server to the nomadic server of theidentified vehicle upon arrival; initiate communication delivery of asecond one of the electronic packages from the fixed content server to asecond destination content server at a second one of the sequence ofdestination locations based on the schedule for arrival of theidentified vehicle transporting the nomadic server to the second one ofthe sequence of destination locations so delivery of the second one ofthe electronic packages is initiated while the identified vehicle istraveling to the second one of the sequence of destination locations andthen uploaded from the second destination content server to the nomadicserver of the identified vehicle upon arrival; obtain informationdefining a schedule for departure of the identified vehicle transportingthe nomadic server from the first one of the sequence of destinationlocations and from the second one of the sequence of destinationlocations; determine a first time to upload the first one of theelectronic packages from the first destination content server to thenomadic server of the identified vehicle and a second time to upload thesecond one of the electronic packages from the second destinationcontent server to the nomadic server of the identified vehicle;provision quality of service that a first network uses to deliver thefirst electronic package from the fixed content server to the firstdestination content server based on the first time to upload, theschedule for arrival of the identified vehicle transporting the nomadicserver to the first one of the sequence of destination locations, andthe schedule for departure of the identified vehicle from the first oneof the sequence of destination locations; and provision quality ofservice that a second network uses to deliver the second electronicpackage from the fixed content server to the second destination contentserver based on the second time to upload, the schedule for arrival ofthe identified vehicle transporting the nomadic server to the second oneof the sequence of destination locations, and the schedule for departureof the identified vehicle from the second one of the sequence ofdestination locations.
 2. The system of claim 1, wherein the processingcircuit of the fixed content server is further configured to: identify aremainder portion of the first one of the electronic packages which didnot complete upload from the first destination content server to thenomadic server before a departure time of the identified vehicle fromthe first one of the sequence of destination locations; and initiatecommunication delivery of the remainder portion of the first one of theelectronic packages from the fixed content server to the seconddestination content server at the second one of the sequence ofdestination locations based on the schedule for arrival of theidentified vehicle transporting the nomadic server to the second one ofthe sequence of destination locations so delivery of the remainderportion of the first one of the electronic packages is initiated whilethe identified vehicle is traveling to the second one of the sequence ofdestination locations and then uploaded from the second destinationcontent server to the nomadic server of the identified vehicle uponarrival.
 3. The system of claim 2, wherein the processing circuit of thefixed content server is further configured to: receive a report from thefirst destination content server at the first one of the sequence ofdestination locations; and identify the remainder portion of the firstone of the electronic packages which did not complete upload from thefirst destination content server to the nomadic server before thedeparture time of the identified vehicle from the first one of thesequence of destination locations based on the report.
 4. The system ofclaim 1, wherein: the provision the quality of service that the firstnetwork uses to deliver the first electronic package, comprises managingthroughput that the first network uses to deliver the first electronicpackage from the fixed content server to the first destination contentserver based on the first time to upload, the schedule for arrival ofthe identified vehicle transporting the nomadic server to the first oneof the sequence of destination locations and the schedule for departureof the identified vehicle from the first one of the sequence ofdestination locations; and the provision the quality of service that thesecond network uses to deliver the second electronic package, comprisesmanaging throughput that the second network uses to deliver the secondelectronic package from the fixed content server to the seconddestination content server based on the second time to upload, theschedule for arrival of the identified vehicle transporting the nomadicserver to the second one of the sequence of destination locations andthe schedule for departure of the identified vehicle from the second oneof the sequence of destination locations.
 5. The system of claim 1,wherein the processing circuit of the fixed content server is furtherconfigured to initiate communication delivery of the first one of theelectronic packages from the fixed content server to the firstdestination content server at the first one of the sequence ofdestination locations based on: determining a speed of the firstnetwork; determining a communication delivery time based on size of thefirst one of the electronic packages and the speed of the first network;determining a remaining time before arrival of the identified one of thevehicles at the first one of the sequence of destination locations basedon the schedule for arrival of the identified vehicle to the first oneof the sequence of destination locations; and initiate communicationdelivery of the first one of the electronic packages from the fixedcontent server to the first destination content server based on thecommunication delivery time and the remaining time before arrival of theidentified one of the vehicles so delivery of the first one of theelectronic packages is completed while the identified one of thevehicles is traveling to the first one of the sequence of destinationlocations and then uploaded from the first destination content server tothe nomadic server of the identified one of the vehicles upon arrival.6. The system of claim 5, wherein the processing circuit of the fixedcontent server is further configured to: initiate communication deliveryof the first one of the electronic packages from the fixed contentserver to the first destination content server based on the first timeto upload, the communication delivery time, and the remaining time sodelivery of the first one of the electronic packages is completed whilethe identified one of the vehicles is traveling to the first one of thesequence of destination locations and then uploaded from the firstdestination content server to the nomadic server of the identified oneof the vehicles upon arrival.
 7. The system of claim 1, wherein theprocessing circuit of the fixed content server is further configured to:determine, from the information defining the schedule for arrival, anairport identifier, a gate number, and a tail number associated with theidentified one of the vehicles transporting the nomadic server; andgenerate the first one of the electronic packages to further contain theairport identifier, the gate number, and the tail number associated withthe identified one of the vehicles.
 8. The system of claim 1, whereinthe processing circuit of the fixed content server is further configuredto: determine, from the information defining the schedule for arrival,an airline flight number associated with the identified one of thevehicles; and generate the first one of the electronic packages tofurther contain the airline flight number.